Hi there @phlax! A community member has suggested an improvement to your security advisory. If approved, this change will affect the global advisory listed at github.com/advisories. It will not affect the version listed in your project repository.

This change will be reviewed by our Security Curation Team. If you have thoughts or feedback, please share them in a comment here! If this PR has already been closed, you can start a new community contribution for this advisory

@sekveaja i think this does need a fix - but im not sure this pr fixes

not familiar with this json spec - but i think you need to bump all the last_affected fields patch+1

@phlax it is the first time I report the discrepancy as an user. I'm not sure where to bump as suggested.

its new to me also - but i think the change needs to happen to last_affected - as suggested above - same file - different fields - updating the timestamp wont do anything afaict

Hi @sekveaja! Thank you so much for contributing to the GitHub Advisory Database. This database is free, open, and accessible to all, and it's people like you who make it great. Thanks for choosing to help others. We hope you send in more contributions in the future!

im still not convinced that this fixed or even changed anything - not sure why their system bothered to notify if it just lands regardless

@phlax The fix is very important for security scanning tools as it verifies GHSA as one of the many lookup entries.